Skip to content

feat: Migrate monorepo build system from Nx to TurboRepo by deleting …#173

Merged
BoBeenLee merged 2 commits intomasterfrom
develop
Feb 22, 2026
Merged

feat: Migrate monorepo build system from Nx to TurboRepo by deleting …#173
BoBeenLee merged 2 commits intomasterfrom
develop

Conversation

@BoBeenLee
Copy link
Owner

@BoBeenLee BoBeenLee commented Feb 22, 2026

User description

…Nx configuration and project files, adding TurboRepo configuration, and updating package scripts.


PR Type

Enhancement


Description

  • Migrate monorepo build system from Nx to TurboRepo

  • Remove all Nx dependencies and configuration references

  • Update package.json scripts to use Turbo commands

  • Add Turbo configuration with task definitions

  • Update library package.json files with scripts and entry points

  • Refactor Tailwind configs to remove Nx glob pattern helpers


Diagram Walkthrough

flowchart LR
  Nx["Nx Build System"] -->|Remove Dependencies| NxDeps["@nx/* packages"]
  Nx -->|Remove Config| NxConfig["nx.json, project.json"]
  Turbo["TurboRepo"] -->|Add Config| TurboJSON["turbo.json"]
  Turbo -->|Update Scripts| Scripts["package.json scripts"]
  Scripts -->|Use turbo run| Commands["turbo run build/dev/lint/test"]
  TailwindConfigs["Tailwind Configs"] -->|Remove| NxGlob["createGlobPatternsForDependencies"]
  TailwindConfigs -->|Add| JoinPath["join() path patterns"]
Loading

File Walkthrough

Relevant files
Configuration changes
14 files
turbo.json
Add TurboRepo configuration file                                                 
+32/-0   
next.config.js
Remove Nx plugin and expand transpile packages                     
+13/-16 
package.json
Add scripts and workspace dependencies                                     
+17/-1   
tailwind.config.js
Replace Nx glob helper with manual path join                         
+1/-3     
tailwind.config.js
Replace Nx glob helper with manual path join                         
+1/-2     
tailwind.config.js
Remove Nx glob helper dependency                                                 
+1/-3     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
package.json
Add scripts and entry point definitions                                   
+7/-1     
Dependencies
1 files
package.json
Replace Nx with Turbo commands and dependencies                   
+22/-38 
Additional files
12 files
project.json +0/-90   
project.json +0/-39   
project.json +0/-39   
project.json +0/-54   
project.json +0/-50   
project.json +0/-39   
project.json +0/-39   
project.json +0/-75   
project.json +0/-39   
nx.json +0/-77   
pnpm-lock.yaml [link]   
project.json +0/-65   

…Nx configuration and project files, adding TurboRepo configuration, and updating package scripts.
@qodo-code-review
Copy link

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
🟢
Generic: Comprehensive Audit Trails

Objective: To create a detailed and reliable record of critical system actions for security analysis
and compliance.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Meaningful Naming and Self-Documenting Code

Objective: Ensure all identifiers clearly express their purpose and intent, making code
self-documenting

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Robust Error Handling and Edge Case Management

Objective: Ensure comprehensive error handling that provides meaningful context and graceful
degradation

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Error Handling

Objective: To prevent the leakage of sensitive system information through error messages while
providing sufficient detail for internal debugging.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Secure Logging Practices

Objective: To ensure logs are useful for debugging and auditing without exposing sensitive
information like PII, PHI, or cardholder data.

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Generic: Security-First Input Validation and Data Handling

Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent
vulnerabilities

Status: Passed

Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

@BoBeenLee BoBeenLee merged commit c8e126b into master Feb 22, 2026
12 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant